Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41dbadc6a8704a547844c859c134556d7ec4db24d18ddc0a47d6273e98479833

Tx prefix hash: 0f3bb6d408cb3590734f141236d82d13cd255c30edbd64ba83942a452a1abfde
Tx public key: a1cae42a7ab81b6bd572418155e9ebe21f7bbb508dd397303ee952a95642ef7a
Timestamp: 1700123182 Timestamp [UCT]: 2023-11-16 08:26:22 Age [y:d:h:m:s]: 01:062:04:23:08
Block: 892767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305833 RingCT/type: yes/0
Extra: 01a1cae42a7ab81b6bd572418155e9ebe21f7bbb508dd397303ee952a95642ef7a02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.681695363000 dcy

stealth address amount amount idx
00: 3f9586a78db875f4aa6a6fc305a914c5d84c8424d6234b6ef4a3b0439270959d 0.681695363000 1348896 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": 892777, "vin": [ { "gen": { "height": 892767 } } ], "vout": [ { "amount": 681695363, "target": { "key": "3f9586a78db875f4aa6a6fc305a914c5d84c8424d6234b6ef4a3b0439270959d" } } ], "extra": [ 1, 161, 202, 228, 42, 122, 184, 27, 107, 213, 114, 65, 129, 85, 233, 235, 226, 31, 123, 187, 80, 141, 211, 151, 48, 62, 233, 82, 169, 86, 66, 239, 122, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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