Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71af53ca759e91231c84a6738df9ec3f43fd3efe29cfa7c1048425c51240f17f

Tx prefix hash: bca25d8a4a2ed917f6a7afe998401f64fb470e44529aa5a5b10483e60d3cd92f
Tx public key: 458839eee2269994e6c0819249353f87dec64ae8090f78e0bf1e6923a4b3e2dd
Timestamp: 1699199012 Timestamp [UCT]: 2023-11-05 15:43:32 Age [y:d:h:m:s]: 01:364:15:19:27
Block: 885106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519519 RingCT/type: yes/0
Extra: 01458839eee2269994e6c0819249353f87dec64ae8090f78e0bf1e6923a4b3e2dd021100000001faf35c9c000000000000000000

1 output(s) for total of 0.716599337000 dcy

stealth address amount amount idx
00: e769474fb563c1cb4d48c98b766ae4c27c142883f75449f4ae950d22440a95a8 0.716599337000 1340859 of 0

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": 885116, "vin": [ { "gen": { "height": 885106 } } ], "vout": [ { "amount": 716599337, "target": { "key": "e769474fb563c1cb4d48c98b766ae4c27c142883f75449f4ae950d22440a95a8" } } ], "extra": [ 1, 69, 136, 57, 238, 226, 38, 153, 148, 230, 192, 129, 146, 73, 53, 63, 135, 222, 198, 74, 232, 9, 15, 120, 224, 191, 30, 105, 35, 164, 179, 226, 221, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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