Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 247307ccb8a5799166c41a7673cb6e477709007471ea856c32ae60ada4b927af

Tx prefix hash: 7a882e9f92552bce6765946fad62a73f567bc4bddaec1dd8c24aadce79aaecec
Tx public key: a3d4d42e2b52ed8009c1831ec25e5976e1b1740e94e885c96c4a76e694f07d41
Timestamp: 1751314192 Timestamp [UCT]: 2025-06-30 20:09:52 Age [y:d:h:m:s]: 00:138:06:18:18
Block: 1316070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97009 RingCT/type: yes/0
Extra: 01a3d4d42e2b52ed8009c1831ec25e5976e1b1740e94e885c96c4a76e694f07d4102110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d14c114acc8b770d047a906092e0453ac8772e5e40c7c7eb0ef0e8a2da024f0b 0.600000000000 1803727 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": 1316080, "vin": [ { "gen": { "height": 1316070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d14c114acc8b770d047a906092e0453ac8772e5e40c7c7eb0ef0e8a2da024f0b" } } ], "extra": [ 1, 163, 212, 212, 46, 43, 82, 237, 128, 9, 193, 131, 30, 194, 94, 89, 118, 225, 177, 116, 14, 148, 232, 133, 201, 108, 74, 118, 230, 148, 240, 125, 65, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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