Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 532ff015e682096b4c20a7b8e2ca0f8446ea8ca6228a6073f56c38db1ef8d710

Tx prefix hash: 8f76a6e046d448f46e76c9ab4225878b1a609a711c4999f7c1cd8a3b68f6d4b3
Tx public key: ed623c81af0824691bb8ed95e9f3f4a0b46b47b37a3735fd24907ad95271e5b2
Timestamp: 1701383391 Timestamp [UCT]: 2023-11-30 22:29:51 Age [y:d:h:m:s]: 01:084:17:57:14
Block: 903212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321683 RingCT/type: yes/0
Extra: 01ed623c81af0824691bb8ed95e9f3f4a0b46b47b37a3735fd24907ad95271e5b202110000000146113aa8000000000000000000

1 output(s) for total of 0.624142393000 dcy

stealth address amount amount idx
00: e50c81869cb40073d480d331118d32a74449816e2f3626863a836927149e878c 0.624142393000 1359883 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": 903222, "vin": [ { "gen": { "height": 903212 } } ], "vout": [ { "amount": 624142393, "target": { "key": "e50c81869cb40073d480d331118d32a74449816e2f3626863a836927149e878c" } } ], "extra": [ 1, 237, 98, 60, 129, 175, 8, 36, 105, 27, 184, 237, 149, 233, 243, 244, 160, 180, 107, 71, 179, 122, 55, 53, 253, 36, 144, 122, 217, 82, 113, 229, 178, 2, 17, 0, 0, 0, 1, 70, 17, 58, 168, 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