Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d59e5a2f93aea96c4786e6b7ecdc5113b28e1495d63f5d4e90d9fa679a1b1be

Tx prefix hash: 10a01b4e7bbe5420343de2aa86089ecd51092a18ec5b70b3f7d4a02d76c6f0eb
Tx public key: 1078328130b85a2f4619f8bda61becb3c70349b4fc4fa11ad895cea944ab89f7
Timestamp: 1694058511 Timestamp [UCT]: 2023-09-07 03:48:31 Age [y:d:h:m:s]: 01:170:13:21:19
Block: 842665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382970 RingCT/type: yes/0
Extra: 011078328130b85a2f4619f8bda61becb3c70349b4fc4fa11ad895cea944ab89f702110000000e4b8f5122000000000000000000

1 output(s) for total of 0.990606368000 dcy

stealth address amount amount idx
00: 7b28a122e9e5956542e950a6491377153967721a40539ac49a8c8c12ffac3aa1 0.990606368000 1295807 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": 842675, "vin": [ { "gen": { "height": 842665 } } ], "vout": [ { "amount": 990606368, "target": { "key": "7b28a122e9e5956542e950a6491377153967721a40539ac49a8c8c12ffac3aa1" } } ], "extra": [ 1, 16, 120, 50, 129, 48, 184, 90, 47, 70, 25, 248, 189, 166, 27, 236, 179, 199, 3, 73, 180, 252, 79, 161, 26, 216, 149, 206, 169, 68, 171, 137, 247, 2, 17, 0, 0, 0, 14, 75, 143, 81, 34, 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