Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3585ace6be81431b9797519a7cee9d21401bd1ec07d71335e0962c822efce41

Tx prefix hash: bc5939ceebbe4738630b89000595e6eb9d32f230d1f916c5fd08f504e618ce94
Tx public key: 6200a4bc9b79d72b8784e47316302b00f8f1b71135f11e987669ac2a4c187be7
Timestamp: 1750715150 Timestamp [UCT]: 2025-06-23 21:45:50 Age [y:d:h:m:s]: 00:143:13:00:32
Block: 1311383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100510 RingCT/type: yes/0
Extra: 016200a4bc9b79d72b8784e47316302b00f8f1b71135f11e987669ac2a4c187be7021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1ad4ebfc47f8ecb8d959566a83ff41403a8b26b743f5c88a6b860b2aee313b8 0.600000000000 1799010 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": 1311393, "vin": [ { "gen": { "height": 1311383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1ad4ebfc47f8ecb8d959566a83ff41403a8b26b743f5c88a6b860b2aee313b8" } } ], "extra": [ 1, 98, 0, 164, 188, 155, 121, 215, 43, 135, 132, 228, 115, 22, 48, 43, 0, 248, 241, 183, 17, 53, 241, 30, 152, 118, 105, 172, 42, 76, 24, 123, 231, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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