Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60c25a26b3bcfad3d7e297a81c9df2dfc759e0bcd8cee9e5033afec4ab0ab3e3

Tx prefix hash: 4fbb31c260f6ab993e066e41ac50c44b1de7890baa07ca0f3695c5e16bc1e4f5
Tx public key: 2ba30232dff8023e3bdcdb31db30d2f3e4e573583042d7663310fb61dde0c73a
Timestamp: 1711298493 Timestamp [UTC]: 2024-03-24 16:41:33 Age [y:d:h:m:s]: 02:048:16:57:45
Block: 985433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546583 RingCT/type: yes/0
Extra: 012ba30232dff8023e3bdcdb31db30d2f3e4e573583042d7663310fb61dde0c73a0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aef534bfc49274f1bedd9217875d9b2afbd183210419e84e458c918fba9755de 0.000600000000 1445644 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": 985443, "vin": [ { "gen": { "height": 985433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aef534bfc49274f1bedd9217875d9b2afbd183210419e84e458c918fba9755de" } } ], "extra": [ 1, 43, 163, 2, 50, 223, 248, 2, 62, 59, 220, 219, 49, 219, 48, 210, 243, 228, 229, 115, 88, 48, 66, 215, 102, 51, 16, 251, 97, 221, 224, 199, 58, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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: