Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e039971508b49cb50c44065020e2fa8eb32eab63ce2c497e1074ca7caf9cfd3a

Tx prefix hash: 43d0d5dbb105d4ba2b43b8c091c5c0d8255d4ac5f46fa1cf495ab011a70db3ec
Tx public key: 54237d0036f709eeaa72ee8948df1e7697f1d1d2d8600efa9f6a14eea9402285
Timestamp: 1720675646 Timestamp [UCT]: 2024-07-11 05:27:26 Age [y:d:h:m:s]: 00:297:21:51:05
Block: 1063168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212850 RingCT/type: yes/0
Extra: 0154237d0036f709eeaa72ee8948df1e7697f1d1d2d8600efa9f6a14eea9402285021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6401950bf8fb31ab376411cb5f58428fa4e6732814dcb1f6339bfc95d1078947 0.600000000000 1533683 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": 1063178, "vin": [ { "gen": { "height": 1063168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6401950bf8fb31ab376411cb5f58428fa4e6732814dcb1f6339bfc95d1078947" } } ], "extra": [ 1, 84, 35, 125, 0, 54, 247, 9, 238, 170, 114, 238, 137, 72, 223, 30, 118, 151, 241, 209, 210, 216, 96, 14, 250, 159, 106, 20, 238, 169, 64, 34, 133, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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