Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d72ec5784a8e4e8bc58ac6e64c0f6feb2b9cf3b43a9f898d21ed41ee6e5c355

Tx prefix hash: 0829e85d7c73673b8fb3eb6e6bd41d0ce886dd39142acbaa88a5c6b402fcca97
Tx public key: a6ceffa4c293e640eb2e6c266a39894c62950b3243396c1c10348c084779b1a0
Timestamp: 1759800677 Timestamp [UCT]: 2025-10-07 01:31:17 Age [y:d:h:m:s]: 00:077:17:03:31
Block: 1384405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55635 RingCT/type: yes/0
Extra: 01a6ceffa4c293e640eb2e6c266a39894c62950b3243396c1c10348c084779b1a002110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd8076d9e8e46cd1a150ecad5f067c07a98e4c1d0fdd6c633014953ef5ffca07 0.600000000000 1872558 of 15

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": 1384415, "vin": [ { "gen": { "height": 1384405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd8076d9e8e46cd1a150ecad5f067c07a98e4c1d0fdd6c633014953ef5ffca07" } } ], "extra": [ 1, 166, 206, 255, 164, 194, 147, 230, 64, 235, 46, 108, 38, 106, 57, 137, 76, 98, 149, 11, 50, 67, 57, 108, 28, 16, 52, 140, 8, 71, 121, 177, 160, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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