Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7389fe2275cb1b61acfc5ef6ff5c9406052c04d08a18087d780d81ca5bf9727

Tx prefix hash: e459cb93835568c88489c54f8d0635c30f70f348c5fdab4bcda155665ed2a724
Tx public key: 70bff6600d520b4a2d6601fc542d50fb50d1628179f381aa9d469e8bcbf5c0bb
Timestamp: 1739142180 Timestamp [UTC]: 2025-02-09 23:03:00 Age [y:d:h:m:s]: 01:107:10:29:57
Block: 1215818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329407 RingCT/type: yes/0
Extra: 0170bff6600d520b4a2d6601fc542d50fb50d1628179f381aa9d469e8bcbf5c0bb02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 51904d91c4f4d9b680ba11e8eb94a808f77e1897fd790f8eebe5e904524f4b49 0.000600000000 1702617 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": 1215828, "vin": [ { "gen": { "height": 1215818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51904d91c4f4d9b680ba11e8eb94a808f77e1897fd790f8eebe5e904524f4b49" } } ], "extra": [ 1, 112, 191, 246, 96, 13, 82, 11, 74, 45, 102, 1, 252, 84, 45, 80, 251, 80, 209, 98, 129, 121, 243, 129, 170, 157, 70, 158, 139, 203, 245, 192, 187, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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: