Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 585f74ae0c169e23ae9945fe07dede561086bfa26dfbb419171d83940a4b99b9

Tx prefix hash: 756695bb312a84d5ee893cdae6ddf05683711c215625c9c97030f7576f061264
Tx public key: 678604e09dba3265d788a1bf4de67c6a2b74bc92da5ebebfb222e1dbd5c5ea27
Timestamp: 1756280978 Timestamp [UCT]: 2025-08-27 07:49:38 Age [y:d:h:m:s]: 00:156:19:21:35
Block: 1355421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111913 RingCT/type: yes/0
Extra: 01678604e09dba3265d788a1bf4de67c6a2b74bc92da5ebebfb222e1dbd5c5ea270211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee8c4564d1b98dd61b71d1d9848efe27a30f2ae8fd2ea73119cb8e7a44f51429 0.600000000000 1843420 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": 1355431, "vin": [ { "gen": { "height": 1355421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee8c4564d1b98dd61b71d1d9848efe27a30f2ae8fd2ea73119cb8e7a44f51429" } } ], "extra": [ 1, 103, 134, 4, 224, 157, 186, 50, 101, 215, 136, 161, 191, 77, 230, 124, 106, 43, 116, 188, 146, 218, 94, 190, 191, 178, 34, 225, 219, 213, 197, 234, 39, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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