Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e6d3bae07cbb37fc005c3d92bffec810fc32e5572df811f12aa0b16a3091fa3

Tx prefix hash: 0f849a39cd792f66024e7c1e99f6cccb68cebdf8541b978577a5023f94d42b51
Tx public key: 24f9f695e835fdcab8b7916e96a3afbc68df667f00d8138e1656b335b2225880
Timestamp: 1735429156 Timestamp [UCT]: 2024-12-28 23:39:16 Age [y:d:h:m:s]: 00:100:10:15:49
Block: 1185342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71553 RingCT/type: yes/0
Extra: 0124f9f695e835fdcab8b7916e96a3afbc68df667f00d8138e1656b335b22258800211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6692d461c8a287d0ed517dc426c2f6c2396edea3bcd26b424cc6c8f72127e0a8 0.600000000000 1671809 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": 1185352, "vin": [ { "gen": { "height": 1185342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6692d461c8a287d0ed517dc426c2f6c2396edea3bcd26b424cc6c8f72127e0a8" } } ], "extra": [ 1, 36, 249, 246, 149, 232, 53, 253, 202, 184, 183, 145, 110, 150, 163, 175, 188, 104, 223, 102, 127, 0, 216, 19, 142, 22, 86, 179, 53, 178, 34, 88, 128, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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