Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd7d1ad949eacde21eea3c3d400a6d803c123d9a37db63d271edec2db9c243a4

Tx prefix hash: b1bc26ec8309825eeb3bc23a15fb20710e97f8c5417f08ab1c6044f35a2687ff
Tx public key: 3e2ef5455aaf69385e1b72d534b77ab30800ed7004eb5074b05d8e236d263711
Timestamp: 1758699639 Timestamp [UCT]: 2025-09-24 07:40:39 Age [y:d:h:m:s]: 00:120:01:53:56
Block: 1375279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85844 RingCT/type: yes/0
Extra: 013e2ef5455aaf69385e1b72d534b77ab30800ed7004eb5074b05d8e236d263711021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06551c1bb4e8ecfa0020f3108db5ab4d8b787fb5895f8c64cb09df876eea2d25 0.600000000000 1863364 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": 1375289, "vin": [ { "gen": { "height": 1375279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06551c1bb4e8ecfa0020f3108db5ab4d8b787fb5895f8c64cb09df876eea2d25" } } ], "extra": [ 1, 62, 46, 245, 69, 90, 175, 105, 56, 94, 27, 114, 213, 52, 183, 122, 179, 8, 0, 237, 112, 4, 235, 80, 116, 176, 93, 142, 35, 109, 38, 55, 17, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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