Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99e55f7ae9f0f828e52b544a8550d092ef10eb9a5a2429eb5c2c9bfefd4e8f62

Tx prefix hash: f50689644bbf770ab8b2a858ec008b64832f646a7f76b7086b5848bae17fd975
Tx public key: b1b1adf1e696c646ee3cca4d204ac8b7e95fe8bb00ad1f186f7758c066c547c8
Timestamp: 1705338096 Timestamp [UCT]: 2024-01-15 17:01:36 Age [y:d:h:m:s]: 01:087:16:56:12
Block: 935987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323785 RingCT/type: yes/0
Extra: 01b1b1adf1e696c646ee3cca4d204ac8b7e95fe8bb00ad1f186f7758c066c547c802110000000c0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 662976418de084a788e0813027a8a24c8eab0f398d6e252e60198d41a5eb8e86 0.600000000000 1394009 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": 935997, "vin": [ { "gen": { "height": 935987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "662976418de084a788e0813027a8a24c8eab0f398d6e252e60198d41a5eb8e86" } } ], "extra": [ 1, 177, 177, 173, 241, 230, 150, 198, 70, 238, 60, 202, 77, 32, 74, 200, 183, 233, 95, 232, 187, 0, 173, 31, 24, 111, 119, 88, 192, 102, 197, 71, 200, 2, 17, 0, 0, 0, 12, 0, 17, 5, 91, 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