Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3213b5b40707d504b5c56561565541557c98fa0878bbb59e51ea1aa0222864e6

Tx prefix hash: f6e6a01b6a038eece1fcfd7f97b088a2365b031c3a284f4cffcca38cd842c35a
Tx public key: cadfecfd03206fd9c8fe78f9317615258dbf5d4c2208463fb1ee8f8af8fab30c
Timestamp: 1737069243 Timestamp [UCT]: 2025-01-16 23:14:03 Age [y:d:h:m:s]: 00:341:02:42:03
Block: 1198916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241343 RingCT/type: yes/0
Extra: 01cadfecfd03206fd9c8fe78f9317615258dbf5d4c2208463fb1ee8f8af8fab30c02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8f648b123a6a1b3ab5354b1106401241d4dff4948acc4231f61eed6433f626e 0.600000000000 1685543 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 dinasty-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": 1198926, "vin": [ { "gen": { "height": 1198916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8f648b123a6a1b3ab5354b1106401241d4dff4948acc4231f61eed6433f626e" } } ], "extra": [ 1, 202, 223, 236, 253, 3, 32, 111, 217, 200, 254, 120, 249, 49, 118, 21, 37, 141, 191, 93, 76, 34, 8, 70, 63, 177, 238, 143, 138, 248, 250, 179, 12, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8