Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be95210dd3c41b34b10ab92c4fbec22a63a53a88cbde37777240d9adef0c37d7

Tx prefix hash: d6da77b3ec5dd6cd31f49e49fafd81ac33980d596a2304a126d6cf80206562b2
Tx public key: 5c205ea5ad7dbcde06c9f9592cd401a9d3a93c75f582e7ca11b07654b173f1ff
Timestamp: 1750885963 Timestamp [UCT]: 2025-06-25 21:12:43 Age [y:d:h:m:s]: 00:147:20:14:38
Block: 1312742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103636 RingCT/type: yes/0
Extra: 015c205ea5ad7dbcde06c9f9592cd401a9d3a93c75f582e7ca11b07654b173f1ff021100000015bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d04408b709eeae5f3b06cef2ad1691d9da59829ef132686b536b32a872cc0a1 0.600000000000 1800377 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": 1312752, "vin": [ { "gen": { "height": 1312742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d04408b709eeae5f3b06cef2ad1691d9da59829ef132686b536b32a872cc0a1" } } ], "extra": [ 1, 92, 32, 94, 165, 173, 125, 188, 222, 6, 201, 249, 89, 44, 212, 1, 169, 211, 169, 60, 117, 245, 130, 231, 202, 17, 176, 118, 84, 177, 115, 241, 255, 2, 17, 0, 0, 0, 21, 191, 81, 178, 162, 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