Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1fcf11545c2444fff88f4d4c2a581a0d9d22c38e7670c8b4fc66b08864506d5

Tx prefix hash: 075d147f85065d29da467cda80eb57ddd0f3210ff6ddc97f35a902bab9cdadb5
Tx public key: e8f49e1a2a81e6c91e974180c2ce3320d94788d87f9ce2fe9f1d2aeb74bab6d0
Timestamp: 1634498580 Timestamp [UCT]: 2021-10-17 19:23:00 Age [y:d:h:m:s]: 03:356:17:20:40
Block: 355090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1030358 RingCT/type: yes/0
Extra: 01e8f49e1a2a81e6c91e974180c2ce3320d94788d87f9ce2fe9f1d2aeb74bab6d00211000000013fc41461000000000000000000

1 output(s) for total of 40.873313023000 dcy

stealth address amount amount idx
00: 04198b0d89b2eeeebff9fef54092e2d72ab0f81beab8b8a7fe7805aafb69a496 40.873313023000 725086 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": 355100, "vin": [ { "gen": { "height": 355090 } } ], "vout": [ { "amount": 40873313023, "target": { "key": "04198b0d89b2eeeebff9fef54092e2d72ab0f81beab8b8a7fe7805aafb69a496" } } ], "extra": [ 1, 232, 244, 158, 26, 42, 129, 230, 201, 30, 151, 65, 128, 194, 206, 51, 32, 217, 71, 136, 216, 127, 156, 226, 254, 159, 29, 42, 235, 116, 186, 182, 208, 2, 17, 0, 0, 0, 1, 63, 196, 20, 97, 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