Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d100193a80a496cc87c3047d8f267929850d0fa5aa3da31beb984237fdb8efd

Tx prefix hash: 3e1bdb7e97cfb0f8610e3e28dd5a1a8d082f3cf1c6761fd283f676dcc55d68e6
Tx public key: 1ae40b5739d0beac60c6568cab19022a436b052faeba50b0e8e2f873b04fcee6
Timestamp: 1694069247 Timestamp [UCT]: 2023-09-07 06:47:27 Age [y:d:h:m:s]: 01:213:16:02:46
Block: 842765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413801 RingCT/type: yes/0
Extra: 011ae40b5739d0beac60c6568cab19022a436b052faeba50b0e8e2f873b04fcee602110000000275e3f0e9000000000000000000

1 output(s) for total of 0.989850881000 dcy

stealth address amount amount idx
00: e914ea4584002347f93edb2c712c1bfb612821e573df5810edbc0dbf77536999 0.989850881000 1295917 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": 842775, "vin": [ { "gen": { "height": 842765 } } ], "vout": [ { "amount": 989850881, "target": { "key": "e914ea4584002347f93edb2c712c1bfb612821e573df5810edbc0dbf77536999" } } ], "extra": [ 1, 26, 228, 11, 87, 57, 208, 190, 172, 96, 198, 86, 140, 171, 25, 2, 42, 67, 107, 5, 47, 174, 186, 80, 176, 232, 226, 248, 115, 176, 79, 206, 230, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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