Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7a4c04a59f0734e56dd9985872453f17a515b2b3417f26f50500b088bd93a53

Tx prefix hash: 43291fe685bcbc7cd7b08f7089bfa5078b1d0375638cc75e06d9fdd8dbed1787
Tx public key: c85b7e2473c8bfad25981a2c0e48fd78edd875dea8b42a8f04da3c54cf4798ce
Timestamp: 1714224852 Timestamp [UCT]: 2024-04-27 13:34:12 Age [y:d:h:m:s]: 01:052:03:26:11
Block: 1009667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298120 RingCT/type: yes/0
Extra: 01c85b7e2473c8bfad25981a2c0e48fd78edd875dea8b42a8f04da3c54cf4798ce02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 756daf393c09fb3ca773d5e986271ade7b7a8bef0622a538f208b87dd236c926 0.600000000000 1471407 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": 1009677, "vin": [ { "gen": { "height": 1009667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "756daf393c09fb3ca773d5e986271ade7b7a8bef0622a538f208b87dd236c926" } } ], "extra": [ 1, 200, 91, 126, 36, 115, 200, 191, 173, 37, 152, 26, 44, 14, 72, 253, 120, 237, 216, 117, 222, 168, 180, 42, 143, 4, 218, 60, 84, 207, 71, 152, 206, 2, 17, 0, 0, 0, 1, 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