Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae993e11cc6070aa5429bb939f10a38b328240d760dc5b7a0fa55bea5594d1bb

Tx prefix hash: 5db1c29aa724e76d7c7b2ca5971438a9e00007d549f0c0afb4e2e2e24dea4975
Tx public key: 3e895a2158934aa7c8ddac669c7be8411fe7bd0d3822f72ac880c4e893470b2a
Timestamp: 1710175456 Timestamp [UCT]: 2024-03-11 16:44:16 Age [y:d:h:m:s]: 00:349:15:35:32
Block: 976117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249972 RingCT/type: yes/0
Extra: 013e895a2158934aa7c8ddac669c7be8411fe7bd0d3822f72ac880c4e893470b2a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba8f06208256fd209504021fb0828ac78961de1173e6e5738a792e644f7a558c 0.600000000000 1436106 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": 976127, "vin": [ { "gen": { "height": 976117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba8f06208256fd209504021fb0828ac78961de1173e6e5738a792e644f7a558c" } } ], "extra": [ 1, 62, 137, 90, 33, 88, 147, 74, 167, 200, 221, 172, 102, 156, 123, 232, 65, 31, 231, 189, 13, 56, 34, 247, 42, 200, 128, 196, 232, 147, 71, 11, 42, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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