Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e79e17ab97dc48f9c5647d0700313141e5738b5df6b3c059e479fcd953156448

Tx prefix hash: a2e7aa934ba5a8621c322ff8e309d89055cd3ee5357b304900d2cd22707e3337
Tx public key: a57e3cfb1ed3061b9eac44a0b035927a705d27100ee3fc268f429c9986b1c157
Timestamp: 1710809446 Timestamp [UCT]: 2024-03-19 00:50:46 Age [y:d:h:m:s]: 00:302:02:19:53
Block: 981379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216226 RingCT/type: yes/0
Extra: 01a57e3cfb1ed3061b9eac44a0b035927a705d27100ee3fc268f429c9986b1c15702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a026a9349dd6f81cb2ad0e29f283b6099d3bd51c5f989250e57e448c37df3632 0.600000000000 1441474 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": 981389, "vin": [ { "gen": { "height": 981379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a026a9349dd6f81cb2ad0e29f283b6099d3bd51c5f989250e57e448c37df3632" } } ], "extra": [ 1, 165, 126, 60, 251, 30, 211, 6, 27, 158, 172, 68, 160, 176, 53, 146, 122, 112, 93, 39, 16, 14, 227, 252, 38, 143, 66, 156, 153, 134, 177, 193, 87, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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