Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab479974921be9dd2384e55d576714ee2edee9cbf5965166cc22197ba0c6ff83

Tx prefix hash: fa8ed64f61b1cdb7549679c54f746bcf9e32bd83773147fe9d7440b74ed001bd
Tx public key: c951cd40ecc49f5881bdf3b73ce891734b24b054fda16562adf7a0aa210daa39
Timestamp: 1636952486 Timestamp [UTC]: 2021-11-15 05:01:26 Age [y:d:h:m:s]: 04:181:21:29:20
Block: 374598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1159446 RingCT/type: yes/0
Extra: 01c951cd40ecc49f5881bdf3b73ce891734b24b054fda16562adf7a0aa210daa39021100000007e59f5d07000000000000000000

1 output(s) for total of 0.035221002284 xmr

stealth address amount amount idx tag
00: 2d897a9dd9216ae8f9d9e2ff9e1f265d9bc0f8a2513b3ff2f86e8a778b5d9cbc 0.035221002284 758184 of 0 -

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": 374608, "vin": [ { "gen": { "height": 374598 } } ], "vout": [ { "amount": 35221002284, "target": { "key": "2d897a9dd9216ae8f9d9e2ff9e1f265d9bc0f8a2513b3ff2f86e8a778b5d9cbc" } } ], "extra": [ 1, 201, 81, 205, 64, 236, 196, 159, 88, 129, 189, 243, 183, 60, 232, 145, 115, 75, 36, 176, 84, 253, 161, 101, 98, 173, 247, 160, 170, 33, 13, 170, 57, 2, 17, 0, 0, 0, 7, 229, 159, 93, 7, 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: