Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 919e982a5a212dce77cd086f415a3fcf8e00cc4d98b32e9547a2a02f1e9e1ee6

Tx prefix hash: c3029411550c79b2fd7f08557d062af084825e3706f0b9c66f55cca5402c8451
Tx public key: 7908e95dd42b20eaaae774a2f9ce59d12b589c72306597e83c8ee2a43c36a74b
Timestamp: 1758158411 Timestamp [UTC]: 2025-09-18 01:20:11 Age [y:d:h:m:s]: 01:059:17:56:33
Block: 1370789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309068 RingCT/type: yes/0
Extra: 017908e95dd42b20eaaae774a2f9ce59d12b589c72306597e83c8ee2a43c36a74b021100000002b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a5133db4d2d37e74fcc82dad2ee1c5019720917ae6469873f64f9f6949384832 0.000600000000 1858866 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": 1370799, "vin": [ { "gen": { "height": 1370789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5133db4d2d37e74fcc82dad2ee1c5019720917ae6469873f64f9f6949384832" } } ], "extra": [ 1, 121, 8, 233, 93, 212, 43, 32, 234, 170, 231, 116, 162, 249, 206, 89, 209, 43, 88, 156, 114, 48, 101, 151, 232, 60, 142, 226, 164, 60, 54, 167, 75, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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: