Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd8a0dc6ba1b66d09cdbac7f0d5ac8b3f9d639beee0ab2e952c8c270f8ad5279

Tx prefix hash: 644870faa84c315222ca0913ac4f8bbe1bae5d9899501fc2ea663fe9853f21c0
Tx public key: b93ea3b7695c2e698e752b531f10471b1312de9c9194f998ff7303c499ca10d7
Timestamp: 1756062425 Timestamp [UCT]: 2025-08-24 19:07:05 Age [y:d:h:m:s]: 00:093:19:25:37
Block: 1353606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66988 RingCT/type: yes/0
Extra: 01b93ea3b7695c2e698e752b531f10471b1312de9c9194f998ff7303c499ca10d70211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0288c6cced3a06380d6968abd8d9e1a53147165908e0e09ad776f4beadb17a28 0.600000000000 1841583 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": 1353616, "vin": [ { "gen": { "height": 1353606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0288c6cced3a06380d6968abd8d9e1a53147165908e0e09ad776f4beadb17a28" } } ], "extra": [ 1, 185, 62, 163, 183, 105, 92, 46, 105, 142, 117, 43, 83, 31, 16, 71, 27, 19, 18, 222, 156, 145, 148, 249, 152, 255, 115, 3, 196, 153, 202, 16, 215, 2, 17, 0, 0, 0, 2, 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