Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b931823ab5cc18dccdbb2f201bca6312e683b22ff0d07203ac6a13933dc2530e

Tx prefix hash: ee6822a9cb1be9a79cf4612d94ba4daf8d6a33dd77534c91534127743f589244
Tx public key: 12e5d0fb42148e8871400de03093996ae5f2d1f56f2ff023a61e316faf6fc72d
Timestamp: 1751136914 Timestamp [UTC]: 2025-06-28 18:55:14 Age [y:d:h:m:s]: 01:137:16:29:51
Block: 1314698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362656 RingCT/type: yes/0
Extra: 0112e5d0fb42148e8871400de03093996ae5f2d1f56f2ff023a61e316faf6fc72d0211000000018368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cd793145f0ba67ee9cc918a65c4213865f7315140eec5fd0b80fc43aa04c6b53 0.000600000000 1802349 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1314708, "vin": [ { "gen": { "height": 1314698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd793145f0ba67ee9cc918a65c4213865f7315140eec5fd0b80fc43aa04c6b53" } } ], "extra": [ 1, 18, 229, 208, 251, 66, 20, 142, 136, 113, 64, 13, 224, 48, 147, 153, 106, 229, 242, 209, 245, 111, 47, 240, 35, 166, 30, 49, 111, 175, 111, 199, 45, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: