Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e81be96c2894336f2c466bea52e38f0afa60ba92d558ce961cb7a01b2804b9b2

Tx prefix hash: 25d9fafd91f1e4243f72b81a248d62c679157527314af2a2f204951c8237c1cb
Tx public key: 8df0a1e954640a4027aaefb9b521a9d1cae0b2c2f137586a9b45b72767b10077
Timestamp: 1634848863 Timestamp [UCT]: 2021-10-21 20:41:03 Age [y:d:h:m:s]: 03:144:18:43:19
Block: 357660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 881546 RingCT/type: yes/0
Extra: 018df0a1e954640a4027aaefb9b521a9d1cae0b2c2f137586a9b45b72767b1007702110000000836fe6557000000000000000000

1 output(s) for total of 40.079690633000 dcy

stealth address amount amount idx
00: db10eee406b89efa3106bfc069b05195b0c2b8682f32ae9599ee1d4750a198e9 40.079690633000 729208 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": 357670, "vin": [ { "gen": { "height": 357660 } } ], "vout": [ { "amount": 40079690633, "target": { "key": "db10eee406b89efa3106bfc069b05195b0c2b8682f32ae9599ee1d4750a198e9" } } ], "extra": [ 1, 141, 240, 161, 233, 84, 100, 10, 64, 39, 170, 239, 185, 181, 33, 169, 209, 202, 224, 178, 194, 241, 55, 88, 106, 155, 69, 183, 39, 103, 177, 0, 119, 2, 17, 0, 0, 0, 8, 54, 254, 101, 87, 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