Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1dbce711d7fade991b47877d0cbf34b562c504982ba4c0b3d6b7a90e0edafb3

Tx prefix hash: 4a9ea574a1aa479492262b52913881a7f9162d44b7a42b80bfb753c85ec96ee7
Tx public key: d96fc65716549b49a4b670d5a0fe016bb54ad73c2dde8fd0e927129ed2f489a4
Timestamp: 1727824115 Timestamp [UCT]: 2024-10-01 23:08:35 Age [y:d:h:m:s]: 00:196:03:10:41
Block: 1122429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139982 RingCT/type: yes/0
Extra: 01d96fc65716549b49a4b670d5a0fe016bb54ad73c2dde8fd0e927129ed2f489a402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 804c7cdc51656f205a15334e22b11b40e651bf253491281c1a7e278882aa2d83 0.600000000000 1604862 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": 1122439, "vin": [ { "gen": { "height": 1122429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "804c7cdc51656f205a15334e22b11b40e651bf253491281c1a7e278882aa2d83" } } ], "extra": [ 1, 217, 111, 198, 87, 22, 84, 155, 73, 164, 182, 112, 213, 160, 254, 1, 107, 181, 74, 215, 60, 45, 222, 143, 208, 233, 39, 18, 158, 210, 244, 137, 164, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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