Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bec06348686109a0d5291337adce159ad2b376d00a2e065c9b96a65b7a972f0a

Tx prefix hash: dc5833390d5283abf8670e1d0201414ac0f10d4d2d1194868599394874af727a
Tx public key: b658ab3f43eb81e1fbbd52050fb6d21a1fbabee3dee519e5a7c885779c1ddfb0
Timestamp: 1771089734 Timestamp [UTC]: 2026-02-14 17:22:14 Age [y:d:h:m:s]: 00:274:21:36:13
Block: 1477768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201951 RingCT/type: yes/0
Extra: 01b658ab3f43eb81e1fbbd52050fb6d21a1fbabee3dee519e5a7c885779c1ddfb0021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 633a22b2f7e3189432533f38287afe9ff4d5595963fb99f7d094f881a7a7040d 0.000600000000 1967088 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": 1477778, "vin": [ { "gen": { "height": 1477768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "633a22b2f7e3189432533f38287afe9ff4d5595963fb99f7d094f881a7a7040d" } } ], "extra": [ 1, 182, 88, 171, 63, 67, 235, 129, 225, 251, 189, 82, 5, 15, 182, 210, 26, 31, 186, 190, 227, 222, 229, 25, 229, 167, 200, 133, 119, 156, 29, 223, 176, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: