Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13e5ab0080dc06e121483b2d814d29cf8a8d5a03cf8e2c2d96947d010a17a8c1

Tx prefix hash: 42d518497f76ca444bc91027e90b4bd7f35fe400b48b352a74dbabd40101c20e
Tx public key: 60666c2928c0b8ff9ba13cf8710b6fa84d2db259a4481eadb6ddf422fe29c6ce
Timestamp: 1721376419 Timestamp [UCT]: 2024-07-19 08:06:59 Age [y:d:h:m:s]: 00:175:22:50:27
Block: 1068980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125883 RingCT/type: yes/0
Extra: 0160666c2928c0b8ff9ba13cf8710b6fa84d2db259a4481eadb6ddf422fe29c6ce021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec71cb4c0e85a4af1a5646e7af6696640549177d124fd21619d32a1ae18fc0fd 0.600000000000 1540223 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": 1068990, "vin": [ { "gen": { "height": 1068980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec71cb4c0e85a4af1a5646e7af6696640549177d124fd21619d32a1ae18fc0fd" } } ], "extra": [ 1, 96, 102, 108, 41, 40, 192, 184, 255, 155, 161, 60, 248, 113, 11, 111, 168, 77, 45, 178, 89, 164, 72, 30, 173, 182, 221, 244, 34, 254, 41, 198, 206, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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