Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b681427236b39bb5932139d1275b819513b072f7cab76fc242cb1165471353b

Tx prefix hash: cf69fd168f1fc95f02aeefce988ec203410ce32fff4857c9580d1356bb6d5996
Tx public key: 2e78a50c26dd051f65a8de006732e3c2748b599d27e74a3f3aa71599c8b6652c
Timestamp: 1582074722 Timestamp [UCT]: 2020-02-19 01:12:02 Age [y:d:h:m:s]: 05:280:04:14:12
Block: 67781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1351108 RingCT/type: yes/0
Extra: 012e78a50c26dd051f65a8de006732e3c2748b599d27e74a3f3aa71599c8b6652c021100000021d81c26c0000000000000000000

1 output(s) for total of 365.943651003000 dcy

stealth address amount amount idx
00: 3495285d004b15685d2e6828b7fa2fe89614ba78057476cce58298b8583fc9c6 365.943651003000 124872 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": 67791, "vin": [ { "gen": { "height": 67781 } } ], "vout": [ { "amount": 365943651003, "target": { "key": "3495285d004b15685d2e6828b7fa2fe89614ba78057476cce58298b8583fc9c6" } } ], "extra": [ 1, 46, 120, 165, 12, 38, 221, 5, 31, 101, 168, 222, 0, 103, 50, 227, 194, 116, 139, 89, 157, 39, 231, 74, 63, 58, 167, 21, 153, 200, 182, 101, 44, 2, 17, 0, 0, 0, 33, 216, 28, 38, 192, 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