Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d81cdd43c626653e241061408d9cd42766700ae9d22730b0f79de40cbf2d74f

Tx prefix hash: cc82b4b82fe292c503a53fab7833b6d1ee15f03b86d529aa3277a63ecb935b2b
Tx public key: fec80c6f6d39aaf9a246dce58fa3f9d9b29b698bbfaf02b0cf34c84231f2503a
Timestamp: 1574564423 Timestamp [UCT]: 2019-11-24 03:00:23 Age [y:d:h:m:s]: 04:343:21:34:04
Block: 16116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1127765 RingCT/type: yes/0
Extra: 01fec80c6f6d39aaf9a246dce58fa3f9d9b29b698bbfaf02b0cf34c84231f2503a02110000000cf95225a5000000000000000000

1 output(s) for total of 542.752564853000 dcy

stealth address amount amount idx
00: 3d9513317bf4abd6a6e5e3bd0f639299be96089b5d6b09f26b96217caceb9a6f 542.752564853000 22300 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": 16126, "vin": [ { "gen": { "height": 16116 } } ], "vout": [ { "amount": 542752564853, "target": { "key": "3d9513317bf4abd6a6e5e3bd0f639299be96089b5d6b09f26b96217caceb9a6f" } } ], "extra": [ 1, 254, 200, 12, 111, 109, 57, 170, 249, 162, 70, 220, 229, 143, 163, 249, 217, 178, 155, 105, 139, 191, 175, 2, 176, 207, 52, 200, 66, 49, 242, 80, 58, 2, 17, 0, 0, 0, 12, 249, 82, 37, 165, 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