Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6932cc37f6c9601fd80ca1f60e44879949702bedcd9ae766cb3cf1bdd688f3ce

Tx prefix hash: 4a28b6ba65b92fc24d6076cf39dd18f18498fe8ca8aee86968dd1574c4832399
Tx public key: d206e2d5d17bd1b2a769e0b0d6e6734a3604637fdc4bdb7bb9dbf830ead210aa
Timestamp: 1764288059 Timestamp [UCT]: 2025-11-28 00:00:59 Age [y:d:h:m:s]: 00:036:13:43:24
Block: 1421600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26187 RingCT/type: yes/0
Extra: 01d206e2d5d17bd1b2a769e0b0d6e6734a3604637fdc4bdb7bb9dbf830ead210aa0211000000044e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbf966df4e999f2d4318ba1aa1276c8467ea851b2f676d92134cf9f2e5c33cd8 0.600000000000 1910157 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": 1421610, "vin": [ { "gen": { "height": 1421600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbf966df4e999f2d4318ba1aa1276c8467ea851b2f676d92134cf9f2e5c33cd8" } } ], "extra": [ 1, 210, 6, 226, 213, 209, 123, 209, 178, 167, 105, 224, 176, 214, 230, 115, 74, 54, 4, 99, 127, 220, 75, 219, 123, 185, 219, 248, 48, 234, 210, 16, 170, 2, 17, 0, 0, 0, 4, 78, 123, 252, 9, 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