Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9909e91cd133a502f779e72182c2223bd7127b074a38fe4e5a7d33f5fd85791

Tx prefix hash: d8f51471c44b8af9a5df3e2d120f1530ee63e998c79b2f3b365847c953e7cacc
Tx public key: 319142a880c01096467bbae5ae1659a91c1463a2ea9705d2b74b043ff614ae18
Timestamp: 1720870056 Timestamp [UTC]: 2024-07-13 11:27:36 Age [y:d:h:m:s]: 01:300:20:50:48
Block: 1064780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466180 RingCT/type: yes/0
Extra: 01319142a880c01096467bbae5ae1659a91c1463a2ea9705d2b74b043ff614ae1802110000000d91e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 095feb5b4b6439aca52408b1832a9ba63ecdd7ddd5b40de4ffc1b71144b514f2 0.000600000000 1535319 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": 1064790, "vin": [ { "gen": { "height": 1064780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "095feb5b4b6439aca52408b1832a9ba63ecdd7ddd5b40de4ffc1b71144b514f2" } } ], "extra": [ 1, 49, 145, 66, 168, 128, 192, 16, 150, 70, 123, 186, 229, 174, 22, 89, 169, 28, 20, 99, 162, 234, 151, 5, 210, 183, 75, 4, 63, 246, 20, 174, 24, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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: