Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 547b83a19aaef7268cbbb72786a2715a7f82316bd0d9cf51e6e0a7303abbb726

Tx prefix hash: 17571ab26a1347846d08d4981b765e31d2934d16195fe5bcb1beb25170e849d4
Tx public key: daed9cfc9266e8b8d589ed1389bf57d6e8239052afed8e11d03257fd93ddf952
Timestamp: 1699517702 Timestamp [UCT]: 2023-11-09 08:15:02 Age [y:d:h:m:s]: 01:023:03:23:25
Block: 887755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277921 RingCT/type: yes/0
Extra: 01daed9cfc9266e8b8d589ed1389bf57d6e8239052afed8e11d03257fd93ddf952021100000002faf35c9c000000000000000000

1 output(s) for total of 0.702261988000 dcy

stealth address amount amount idx
00: f45bdb7db1a7fa772a69234e8cb7c3ae07e7fa7517c977e02aebf3b01fc7712e 0.702261988000 1343650 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": 887765, "vin": [ { "gen": { "height": 887755 } } ], "vout": [ { "amount": 702261988, "target": { "key": "f45bdb7db1a7fa772a69234e8cb7c3ae07e7fa7517c977e02aebf3b01fc7712e" } } ], "extra": [ 1, 218, 237, 156, 252, 146, 102, 232, 184, 213, 137, 237, 19, 137, 191, 87, 214, 232, 35, 144, 82, 175, 237, 142, 17, 208, 50, 87, 253, 147, 221, 249, 82, 2, 17, 0, 0, 0, 2, 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