Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e77ffa7bd070943a9069c4085bbf9dd5034338d442486b2ba0c8e3405522ad7

Tx prefix hash: 94950039f28ba38af3d615ddb007ebbfb6bb03d92c3d2d5fc32dc684af89ff65
Tx public key: 9e7a786e5fca12298ee7e87faacac46f81aafb2d22d231bf4fee34fa4aa62a02
Timestamp: 1704890517 Timestamp [UCT]: 2024-01-10 12:41:57 Age [y:d:h:m:s]: 01:046:22:50:58
Block: 932279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294627 RingCT/type: yes/0
Extra: 019e7a786e5fca12298ee7e87faacac46f81aafb2d22d231bf4fee34fa4aa62a020211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c734a7e0298f251cf9c831c411f02b7e27a51c161437bbf687f8ee6222c4815b 0.600000000000 1390211 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": 932289, "vin": [ { "gen": { "height": 932279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c734a7e0298f251cf9c831c411f02b7e27a51c161437bbf687f8ee6222c4815b" } } ], "extra": [ 1, 158, 122, 120, 110, 95, 202, 18, 41, 142, 231, 232, 127, 170, 202, 196, 111, 129, 170, 251, 45, 34, 210, 49, 191, 79, 238, 52, 250, 74, 166, 42, 2, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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