Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 527b67d2e3a5da71e7aa5e840a80e9dbd600cbd50043db11c7c62db9518636fb

Tx prefix hash: 9c7652f694d27f49138c7cbdee5e35eccde6d0caac344a0f289c967f403e7609
Tx public key: 0cec52b03a2ac26ca8dcf4046bd02208ce2a4c3d0e8dd8827fd45c085327f3af
Timestamp: 1765974218 Timestamp [UCT]: 2025-12-17 12:23:38 Age [y:d:h:m:s]: 00:005:00:18:41
Block: 1435564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3593 RingCT/type: yes/0
Extra: 010cec52b03a2ac26ca8dcf4046bd02208ce2a4c3d0e8dd8827fd45c085327f3af0211000000047b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0573ea0158f05983f880b4af4f059ad7f091290bb319045087970e525e030064 0.600000000000 1924361 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": 1435574, "vin": [ { "gen": { "height": 1435564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0573ea0158f05983f880b4af4f059ad7f091290bb319045087970e525e030064" } } ], "extra": [ 1, 12, 236, 82, 176, 58, 42, 194, 108, 168, 220, 244, 4, 107, 208, 34, 8, 206, 42, 76, 61, 14, 141, 216, 130, 127, 212, 92, 8, 83, 39, 243, 175, 2, 17, 0, 0, 0, 4, 123, 30, 81, 172, 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