Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ca1526dfbb046cb2ceda37362209ec71922e5678853eeb281e323b78a92c870

Tx prefix hash: 4a743ab9ac4761e70c6e24adb45860e8a5fbd9997f112ff1da1b4c61f20ab6c0
Tx public key: a81ce8415bf2c1b5fb9725ea6635f429cdb57c163aadc9c9bf2d5dad8e40d5cc
Timestamp: 1687062518 Timestamp [UCT]: 2023-06-18 04:28:38 Age [y:d:h:m:s]: 01:347:01:00:34
Block: 784735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509244 RingCT/type: yes/0
Extra: 01a81ce8415bf2c1b5fb9725ea6635f429cdb57c163aadc9c9bf2d5dad8e40d5cc02110000000133af99f4000000000000000000

1 output(s) for total of 1.541158615000 dcy

stealth address amount amount idx
00: e3e26c4d9248c801c4b9f2128cced3e13d191e2c591c13769fcd1ebf461262c7 1.541158615000 1234634 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": 784745, "vin": [ { "gen": { "height": 784735 } } ], "vout": [ { "amount": 1541158615, "target": { "key": "e3e26c4d9248c801c4b9f2128cced3e13d191e2c591c13769fcd1ebf461262c7" } } ], "extra": [ 1, 168, 28, 232, 65, 91, 242, 193, 181, 251, 151, 37, 234, 102, 53, 244, 41, 205, 181, 124, 22, 58, 173, 201, 201, 191, 45, 93, 173, 142, 64, 213, 204, 2, 17, 0, 0, 0, 1, 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