Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc5fb0a31f7e2cef7cdcceeba473f4861216204812640b4c2cace98a645909e0

Tx prefix hash: b131b2a6e325f22a30adc7ef5c890effc902b18fbf195a5cf6d45dca6a9a46b6
Tx public key: 7b372ec5000b20a5f808bd9e7a48841b7a8dae1b5e4e980e9260154e7bf3a206
Timestamp: 1685003773 Timestamp [UCT]: 2023-05-25 08:36:13 Age [y:d:h:m:s]: 02:167:09:59:34
Block: 767676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 639439 RingCT/type: yes/0
Extra: 017b372ec5000b20a5f808bd9e7a48841b7a8dae1b5e4e980e9260154e7bf3a20602110000000533af99f4000000000000000000

1 output(s) for total of 1.755379054000 dcy

stealth address amount amount idx
00: b5ac02497c5f73a0e4e05a2b1c1d817fbf1f4405e4fb8b2af64360db4ac572a1 1.755379054000 1216809 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": 767686, "vin": [ { "gen": { "height": 767676 } } ], "vout": [ { "amount": 1755379054, "target": { "key": "b5ac02497c5f73a0e4e05a2b1c1d817fbf1f4405e4fb8b2af64360db4ac572a1" } } ], "extra": [ 1, 123, 55, 46, 197, 0, 11, 32, 165, 248, 8, 189, 158, 122, 72, 132, 27, 122, 141, 174, 27, 94, 78, 152, 14, 146, 96, 21, 78, 123, 243, 162, 6, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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