Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4b4a9b1d8f68a24ea86105ca0d748a9f7a7fad8e91e3e39bebe086da66e11e9

Tx prefix hash: dfac7223969f09bf51c73924052f35cfd5e79c55684142216dff9a1d0d9a0e7d
Tx public key: 2b40645b59a7e1c3fc3f783707896b75aff1c6053c0e4497251432378110a3f0
Timestamp: 1581375885 Timestamp [UCT]: 2020-02-10 23:04:45 Age [y:d:h:m:s]: 05:242:03:29:28
Block: 62431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1323441 RingCT/type: yes/0
Extra: 012b40645b59a7e1c3fc3f783707896b75aff1c6053c0e4497251432378110a3f002110000000d8a2ee0d9000000000000000000

1 output(s) for total of 381.189558011000 dcy

stealth address amount amount idx
00: c2c0c6e7c62ee53cd1ea8b1425fb943faaa1393b3843c171e0edfc88d2aeb445 381.189558011000 115175 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": 62441, "vin": [ { "gen": { "height": 62431 } } ], "vout": [ { "amount": 381189558011, "target": { "key": "c2c0c6e7c62ee53cd1ea8b1425fb943faaa1393b3843c171e0edfc88d2aeb445" } } ], "extra": [ 1, 43, 64, 100, 91, 89, 167, 225, 195, 252, 63, 120, 55, 7, 137, 107, 117, 175, 241, 198, 5, 60, 14, 68, 151, 37, 20, 50, 55, 129, 16, 163, 240, 2, 17, 0, 0, 0, 13, 138, 46, 224, 217, 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