Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 107c8b7b8200ab60033a26c4c742e33aa8ca08cbd7f9861d5ce3d2e1e7b0360c

Tx prefix hash: 7d8cda3e02029c2ea3ee2456541ee4387ea90a453c4f5eafab226e490f317168
Tx public key: 3c3f1ca94bb1b5e5dc2f3d25f8415540be6d78cfb66946de215ec8cc77a0f5c0
Timestamp: 1711801538 Timestamp [UCT]: 2024-03-30 12:25:38 Age [y:d:h:m:s]: 00:277:07:58:15
Block: 989608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198490 RingCT/type: yes/0
Extra: 013c3f1ca94bb1b5e5dc2f3d25f8415540be6d78cfb66946de215ec8cc77a0f5c002110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0dd2f551ab1e0aae592e2420ae743055fb7873d76ef9f578e881a9ba603717a 0.600000000000 1449907 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": 989618, "vin": [ { "gen": { "height": 989608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0dd2f551ab1e0aae592e2420ae743055fb7873d76ef9f578e881a9ba603717a" } } ], "extra": [ 1, 60, 63, 28, 169, 75, 177, 181, 229, 220, 47, 61, 37, 248, 65, 85, 64, 190, 109, 120, 207, 182, 105, 70, 222, 33, 94, 200, 204, 119, 160, 245, 192, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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