Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e92fb043d841df1d2fa8ce01c510ea765c97a7dc9d390025e312ad408485a472

Tx prefix hash: 1b11491003d68275ed22e408771fb9c5d3db65f789ace781ff8cbe90d96abf20
Tx public key: dcc42099b41c07da015bccdffd668febf1673a3ae1c6fff0aa82b59e6048f316
Timestamp: 1704962855 Timestamp [UCT]: 2024-01-11 08:47:35 Age [y:d:h:m:s]: 00:346:11:47:06
Block: 932877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248119 RingCT/type: yes/0
Extra: 01dcc42099b41c07da015bccdffd668febf1673a3ae1c6fff0aa82b59e6048f31602110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a71ba365897100393867efc1a613825ae30964b7e13e85112e5e3d2c9b91e2e0 0.600000000000 1390817 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": 932887, "vin": [ { "gen": { "height": 932877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a71ba365897100393867efc1a613825ae30964b7e13e85112e5e3d2c9b91e2e0" } } ], "extra": [ 1, 220, 196, 32, 153, 180, 28, 7, 218, 1, 91, 204, 223, 253, 102, 143, 235, 241, 103, 58, 58, 225, 198, 255, 240, 170, 130, 181, 158, 96, 72, 243, 22, 2, 17, 0, 0, 0, 9, 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