Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a75af8f53e1364dbcf8116c570c42f0cfb51c364754d8eb23b3802a23cca76a2

Tx prefix hash: 717aadd965f4ccefdf153f1421874db6ebe23eedaeaaddd9216d3711d9ecd7f4
Tx public key: 0a6869580a821f6126eb4acaa4f8d6e3fe4da5cb5ee10e701f914990bf3b2e95
Timestamp: 1761033285 Timestamp [UCT]: 2025-10-21 07:54:45 Age [y:d:h:m:s]: 00:103:04:20:53
Block: 1394634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73680 RingCT/type: yes/0
Extra: 010a6869580a821f6126eb4acaa4f8d6e3fe4da5cb5ee10e701f914990bf3b2e9502110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26649a31e6264f3c161a8dc00b69ba6cc96d0f69a3f94f0a845ee5153d62d01c 0.600000000000 1882909 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": 1394644, "vin": [ { "gen": { "height": 1394634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26649a31e6264f3c161a8dc00b69ba6cc96d0f69a3f94f0a845ee5153d62d01c" } } ], "extra": [ 1, 10, 104, 105, 88, 10, 130, 31, 97, 38, 235, 74, 202, 164, 248, 214, 227, 254, 77, 165, 203, 94, 225, 14, 112, 31, 145, 73, 144, 191, 59, 46, 149, 2, 17, 0, 0, 0, 3, 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