Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fafa6c468acb28d299ae5f7a77355cfe29c5470fd2a3d7a8eb0f51ffc96f519

Tx prefix hash: 64dff24f7f39b97747592df31c861677c7c70d191fdb37206fdb9c69ac8bf33d
Tx public key: 8bc57b1e58fc61e6596013970465041077f7ebc171d62208a08d222ac82570d6
Timestamp: 1682377419 Timestamp [UCT]: 2023-04-24 23:03:39 Age [y:d:h:m:s]: 01:205:02:27:10
Block: 745898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408018 RingCT/type: yes/0
Extra: 018bc57b1e58fc61e6596013970465041077f7ebc171d62208a08d222ac82570d6021100000002b3164c24000000000000000000

1 output(s) for total of 2.072671607000 dcy

stealth address amount amount idx
00: e775c4d2272c70aaf0065e7daa6dc06df8a4481684c4c0d647d962ed90c2c6f3 2.072671607000 1193393 of 0

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": 745908, "vin": [ { "gen": { "height": 745898 } } ], "vout": [ { "amount": 2072671607, "target": { "key": "e775c4d2272c70aaf0065e7daa6dc06df8a4481684c4c0d647d962ed90c2c6f3" } } ], "extra": [ 1, 139, 197, 123, 30, 88, 252, 97, 230, 89, 96, 19, 151, 4, 101, 4, 16, 119, 247, 235, 193, 113, 214, 34, 8, 160, 141, 34, 42, 200, 37, 112, 214, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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