Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d1cea44f9d2a1033ade5d17cafd57468c36fc83aedb8da7ea1d63468e0db0fe

Tx prefix hash: d477954e032bd1e0e0d06767717552c3aa2ddbd6b1f961cd50b5637c5f7d1699
Tx public key: d565a6511ee5507449e0cd810b8a65422b7491f0f640f7f13e129d264429d2db
Timestamp: 1749611255 Timestamp [UCT]: 2025-06-11 03:07:35 Age [y:d:h:m:s]: 00:168:11:00:43
Block: 1302477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118107 RingCT/type: yes/0
Extra: 01d565a6511ee5507449e0cd810b8a65422b7491f0f640f7f13e129d264429d2db021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47520246cf97dc21009efdd8ab44bb4a8eb973c5cc03ca732436d07c8b80e063 0.600000000000 1790048 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": 1302487, "vin": [ { "gen": { "height": 1302477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47520246cf97dc21009efdd8ab44bb4a8eb973c5cc03ca732436d07c8b80e063" } } ], "extra": [ 1, 213, 101, 166, 81, 30, 229, 80, 116, 73, 224, 205, 129, 11, 138, 101, 66, 43, 116, 145, 240, 246, 64, 247, 241, 62, 18, 157, 38, 68, 41, 210, 219, 2, 17, 0, 0, 0, 1, 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