Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 738f2168c7f8c78efe8b603b134638087bd8ade699eeaeb544747424c4cb30e7

Tx prefix hash: d658f369482db96ee6a06252a405be4612a77cfc45c3fcebfdb5b3801c115635
Tx public key: c0d3a7b69d0a2e64fbfbefb19479c9cda8905fba0ff700705db08a06468c03b4
Timestamp: 1705692427 Timestamp [UCT]: 2024-01-19 19:27:07 Age [y:d:h:m:s]: 01:150:07:02:36
Block: 938905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368451 RingCT/type: yes/0
Extra: 01c0d3a7b69d0a2e64fbfbefb19479c9cda8905fba0ff700705db08a06468c03b40211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6cfac177e5555f8559c0377a42a7170e4a960ef0a4d494cd948e81eba3a0a52 0.600000000000 1396987 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": 938915, "vin": [ { "gen": { "height": 938905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6cfac177e5555f8559c0377a42a7170e4a960ef0a4d494cd948e81eba3a0a52" } } ], "extra": [ 1, 192, 211, 167, 182, 157, 10, 46, 100, 251, 251, 239, 177, 148, 121, 201, 205, 168, 144, 95, 186, 15, 247, 0, 112, 93, 176, 138, 6, 70, 140, 3, 180, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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