Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f004365e0e5b2a7d64ca0be228bb01f10ed761e61b1d38093c15a9f64414e7de

Tx prefix hash: 356786f7194a7a0cd5f5ca35d3ebec495211d38a589721d5d962462ba62de6c1
Tx public key: e8f1dd7fb65a60d37d412eb869a3b298da9fcb6f7f5e2f2a84ed4ab15a9b92a7
Timestamp: 1746972699 Timestamp [UCT]: 2025-05-11 14:11:39 Age [y:d:h:m:s]: 00:149:11:26:02
Block: 1280641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104477 RingCT/type: yes/0
Extra: 01e8f1dd7fb65a60d37d412eb869a3b298da9fcb6f7f5e2f2a84ed4ab15a9b92a70211000000049f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 620d9a32e601c3ff80541c55845c12e88a20a1ab9bbb33d2100d5fba4f13f8bc 0.600000000000 1768030 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": 1280651, "vin": [ { "gen": { "height": 1280641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "620d9a32e601c3ff80541c55845c12e88a20a1ab9bbb33d2100d5fba4f13f8bc" } } ], "extra": [ 1, 232, 241, 221, 127, 182, 90, 96, 211, 125, 65, 46, 184, 105, 163, 178, 152, 218, 159, 203, 111, 127, 94, 47, 42, 132, 237, 74, 177, 90, 155, 146, 167, 2, 17, 0, 0, 0, 4, 159, 159, 230, 140, 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