Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a4827efd3ce8c3e269e78783b5c35995fb44b395aac7be3851c1c462495d472

Tx prefix hash: f75fec0a4d26d8a873ed29e2aac518b31eccdb6f303217f4f8ddc4efc117d68d
Tx public key: 63906073957d9873e2379b398d1208a8719531655adc797f9032b6ada1b4a956
Timestamp: 1577835909 Timestamp [UCT]: 2019-12-31 23:45:09 Age [y:d:h:m:s]: 05:070:22:45:24
Block: 36056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200502 RingCT/type: yes/0
Extra: 0163906073957d9873e2379b398d1208a8719531655adc797f9032b6ada1b4a95602110000000c4ac5aa02000000000000000000

1 output(s) for total of 466.165218546000 dcy

stealth address amount amount idx
00: d1faaa4f86051b41d92f59a2756e81b6f001491513891b3932e0f10929f2e5d7 466.165218546000 60942 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": 36066, "vin": [ { "gen": { "height": 36056 } } ], "vout": [ { "amount": 466165218546, "target": { "key": "d1faaa4f86051b41d92f59a2756e81b6f001491513891b3932e0f10929f2e5d7" } } ], "extra": [ 1, 99, 144, 96, 115, 149, 125, 152, 115, 226, 55, 155, 57, 141, 18, 8, 168, 113, 149, 49, 101, 90, 220, 121, 127, 144, 50, 182, 173, 161, 180, 169, 86, 2, 17, 0, 0, 0, 12, 74, 197, 170, 2, 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