Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 852ef1ac5ae7ca9a12727922dd42f6eb3df88bb12b2ad6e11d0a8077de6c9b8e

Tx prefix hash: 93afe85bb36d4d9e41ea59a62c9a56c3cd0ddec85269e6183eab36953fa81b2a
Tx public key: 4dc3fdd4a1a4c5a83b31135329e290da1db8c5dbbe2b6327229020cef82a1f97
Timestamp: 1580112959 Timestamp [UCT]: 2020-01-27 08:15:59 Age [y:d:h:m:s]: 04:333:05:32:07
Block: 53691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128504 RingCT/type: yes/0
Extra: 014dc3fdd4a1a4c5a83b31135329e290da1db8c5dbbe2b6327229020cef82a1f970211000000022264afe6000000000000000000

1 output(s) for total of 407.474331927000 dcy

stealth address amount amount idx
00: 0bb734c5979f1e3b3f4eb6ea11db400da3093e50199d854369f5e0855b1bd5bc 407.474331927000 99545 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": 53701, "vin": [ { "gen": { "height": 53691 } } ], "vout": [ { "amount": 407474331927, "target": { "key": "0bb734c5979f1e3b3f4eb6ea11db400da3093e50199d854369f5e0855b1bd5bc" } } ], "extra": [ 1, 77, 195, 253, 212, 161, 164, 197, 168, 59, 49, 19, 83, 41, 226, 144, 218, 29, 184, 197, 219, 190, 43, 99, 39, 34, 144, 32, 206, 248, 42, 31, 151, 2, 17, 0, 0, 0, 2, 34, 100, 175, 230, 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