Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 404499f267ecfe1183bd787179264b3adfb8401468e2b5508dd1e9a03a18ab23

Tx prefix hash: 216ae2f9ff925ed83fdb1134fde917aae50534e7d347fd528671dfe8be0ae4c7
Tx public key: bfa8c30e9bdf221e61474cae9d1e4af08fe6005cce8879cc677e298d9ce75f2f
Timestamp: 1759173462 Timestamp [UCT]: 2025-09-29 19:17:42 Age [y:d:h:m:s]: 00:020:10:13:25
Block: 1379195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14657 RingCT/type: yes/0
Extra: 01bfa8c30e9bdf221e61474cae9d1e4af08fe6005cce8879cc677e298d9ce75f2f021100000001a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 468c3f05c43ccb2d3a24abba019bd49342b440dfdcc32f6f9eb7c533d66186b0 0.600000000000 1867292 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": 1379205, "vin": [ { "gen": { "height": 1379195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "468c3f05c43ccb2d3a24abba019bd49342b440dfdcc32f6f9eb7c533d66186b0" } } ], "extra": [ 1, 191, 168, 195, 14, 155, 223, 34, 30, 97, 71, 76, 174, 157, 30, 74, 240, 143, 230, 0, 92, 206, 136, 121, 204, 103, 126, 41, 141, 156, 231, 95, 47, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 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