Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae958ee49d35fe98e0db56a28f24d8ff62438fa53c44c251862953960e545845

Tx prefix hash: b96c5cf70335d7d0cf99d3950d6d2d36c85cd7a584823a528c67af6e25f570a9
Tx public key: eed39c5e75f9fb272d10c368be008eb1a70d544e09ee24623805c833b39f6a4d
Timestamp: 1763657438 Timestamp [UCT]: 2025-11-20 16:50:38 Age [y:d:h:m:s]: 00:033:05:58:54
Block: 1416361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23803 RingCT/type: yes/0
Extra: 01eed39c5e75f9fb272d10c368be008eb1a70d544e09ee24623805c833b39f6a4d02110000000b70609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 942c7fd5fa739a823d4a53579d6cef33856047b9420d269f7fa605ec20691d6f 0.600000000000 1904880 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": 1416371, "vin": [ { "gen": { "height": 1416361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "942c7fd5fa739a823d4a53579d6cef33856047b9420d269f7fa605ec20691d6f" } } ], "extra": [ 1, 238, 211, 156, 94, 117, 249, 251, 39, 45, 16, 195, 104, 190, 0, 142, 177, 167, 13, 84, 78, 9, 238, 36, 98, 56, 5, 200, 51, 179, 159, 106, 77, 2, 17, 0, 0, 0, 11, 112, 96, 157, 3, 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