Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a30bb33bb0dbf194f8662819ef51dfd192cb1d2bd689618dca166ced65f1c79

Tx prefix hash: 34da88e77e3fad2aa9e4a32bd06f8fdb51d66837ed6b9762934695d56b1636b1
Tx public key: ff4dd9740568c5b1c688f05cf6393d38a692900c24864ac3fd7ee2ea45483fde
Timestamp: 1694800817 Timestamp [UCT]: 2023-09-15 18:00:17 Age [y:d:h:m:s]: 01:116:20:17:07
Block: 848828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344824 RingCT/type: yes/0
Extra: 01ff4dd9740568c5b1c688f05cf6393d38a692900c24864ac3fd7ee2ea45483fde0211000000014b8f5122000000000000000000

1 output(s) for total of 0.945106019000 dcy

stealth address amount amount idx
00: cc075d0ace0f3a4616718cf38d476b1b128eda83dfbb1e6ec8d6a22eda4137b5 0.945106019000 1302456 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": 848838, "vin": [ { "gen": { "height": 848828 } } ], "vout": [ { "amount": 945106019, "target": { "key": "cc075d0ace0f3a4616718cf38d476b1b128eda83dfbb1e6ec8d6a22eda4137b5" } } ], "extra": [ 1, 255, 77, 217, 116, 5, 104, 197, 177, 198, 136, 240, 92, 246, 57, 61, 56, 166, 146, 144, 12, 36, 134, 74, 195, 253, 126, 226, 234, 69, 72, 63, 222, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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