Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dcebf919d98378a1bfbb3a963eaba16f7bfe5efc118ddc36fe8e578f06df0f8

Tx prefix hash: 622965047d53b147629f312f47249e0f90ba18b0cfe5117838d48918937370b9
Tx public key: 011063e90c6d3781fe9b0a54b9f924dc26938108947f3dbb15505a00375ba04d
Timestamp: 1735902968 Timestamp [UCT]: 2025-01-03 11:16:08 Age [y:d:h:m:s]: 00:306:03:11:18
Block: 1189288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216259 RingCT/type: yes/0
Extra: 01011063e90c6d3781fe9b0a54b9f924dc26938108947f3dbb15505a00375ba04d021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55ceba90fa942bfe73b691ff1620af1f9e7e24e10b8d0a136399a63d1fb245a7 0.600000000000 1675795 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": 1189298, "vin": [ { "gen": { "height": 1189288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55ceba90fa942bfe73b691ff1620af1f9e7e24e10b8d0a136399a63d1fb245a7" } } ], "extra": [ 1, 1, 16, 99, 233, 12, 109, 55, 129, 254, 155, 10, 84, 185, 249, 36, 220, 38, 147, 129, 8, 148, 127, 61, 187, 21, 80, 90, 0, 55, 91, 160, 77, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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