Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5d52d51cac83a063d5091552389c2f545f9f160b14ac8f90d1b9180c93806ef

Tx prefix hash: 590641b8cb1c03ee8184990bd3f344bdbe51b813730588a2a981058ddf437f23
Tx public key: a8d6e992e9e6ec050ebf1e9ec5ec7db307c90546f994d534f632c8eb76ff54e2
Timestamp: 1729367203 Timestamp [UCT]: 2024-10-19 19:46:43 Age [y:d:h:m:s]: 00:215:21:34:27
Block: 1135210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154118 RingCT/type: yes/0
Extra: 01a8d6e992e9e6ec050ebf1e9ec5ec7db307c90546f994d534f632c8eb76ff54e2021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 384d9ce2d27f1db885bbabaa5e8353a8ee996be31c3f007c6ca4579b8c2b38d6 0.600000000000 1618541 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": 1135220, "vin": [ { "gen": { "height": 1135210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "384d9ce2d27f1db885bbabaa5e8353a8ee996be31c3f007c6ca4579b8c2b38d6" } } ], "extra": [ 1, 168, 214, 233, 146, 233, 230, 236, 5, 14, 191, 30, 158, 197, 236, 125, 179, 7, 201, 5, 70, 249, 148, 213, 52, 246, 50, 200, 235, 118, 255, 84, 226, 2, 17, 0, 0, 0, 1, 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