Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edf988f1584add7f38d8cd5837506549ae39cb5d1e5aa2404bd7cc74a27d01df

Tx prefix hash: 80b3b717edbc688ba7e3b923a89ed9ba98b2cb901c06492ec69c959982a6461f
Tx public key: 8e86027d1a968dd80870e5b04cd15deba1a3bfcaac1f1f6820d5f00c65839951
Timestamp: 1751727679 Timestamp [UCT]: 2025-07-05 15:01:19 Age [y:d:h:m:s]: 00:185:09:41:15
Block: 1319327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130931 RingCT/type: yes/0
Extra: 018e86027d1a968dd80870e5b04cd15deba1a3bfcaac1f1f6820d5f00c65839951021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c81ffc565f54e081896b30e5e87047f625e794e8bb017c54189ffd52e702c405 0.600000000000 1807018 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": 1319337, "vin": [ { "gen": { "height": 1319327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c81ffc565f54e081896b30e5e87047f625e794e8bb017c54189ffd52e702c405" } } ], "extra": [ 1, 142, 134, 2, 125, 26, 150, 141, 216, 8, 112, 229, 176, 76, 209, 93, 235, 161, 163, 191, 202, 172, 31, 31, 104, 32, 213, 240, 12, 101, 131, 153, 81, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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