Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12acbca8905585cb371ab9340881ff405c9c753bf3f3d436c758c43c8304c30c

Tx prefix hash: 6f8b9d85e14759dcd888186d5e9d38b14c570f86918636fdea97e240a186a9e6
Tx public key: b7fe5dbd6f0d323286e5940a182c1b368837de03978fbe226b0bb8af38cdb1c9
Timestamp: 1698893622 Timestamp [UCT]: 2023-11-02 02:53:42 Age [y:d:h:m:s]: 02:021:23:44:38
Block: 882775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 535321 RingCT/type: yes/0
Extra: 01b7fe5dbd6f0d323286e5940a182c1b368837de03978fbe226b0bb8af38cdb1c902110000000575e3f0e9000000000000000000

1 output(s) for total of 0.729457470000 dcy

stealth address amount amount idx
00: 8f02c8b0cdf704b0c037c5dc5fc61ae642bccec80b7cb321794983663c4615d4 0.729457470000 1338453 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": 882785, "vin": [ { "gen": { "height": 882775 } } ], "vout": [ { "amount": 729457470, "target": { "key": "8f02c8b0cdf704b0c037c5dc5fc61ae642bccec80b7cb321794983663c4615d4" } } ], "extra": [ 1, 183, 254, 93, 189, 111, 13, 50, 50, 134, 229, 148, 10, 24, 44, 27, 54, 136, 55, 222, 3, 151, 143, 190, 34, 107, 11, 184, 175, 56, 205, 177, 201, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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