Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 086ebced98739496de51180ab5729f096308de937a743191a4588a806b5a38dd

Tx prefix hash: a074c9e14651b6b3c65aa4b0aa4c99ff0bdf5ca5a92f47e83cd7104aa4a3b18f
Tx public key: 53db696367e0f42a20ca2292fc1f41e9cda312804d3330828e21318189f5c9a5
Timestamp: 1576424765 Timestamp [UCT]: 2019-12-15 15:46:05 Age [y:d:h:m:s]: 04:338:02:47:47
Block: 27498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127631 RingCT/type: yes/0
Extra: 0153db696367e0f42a20ca2292fc1f41e9cda312804d3330828e21318189f5c9a5021100000022ad433a0b000000000000000000

1 output(s) for total of 497.609401451000 dcy

stealth address amount amount idx
00: af9f11964bbeb206a857d1277faac8097c8fb2d3f145b9f7f5424ce08ad783dd 497.609401451000 45500 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": 27508, "vin": [ { "gen": { "height": 27498 } } ], "vout": [ { "amount": 497609401451, "target": { "key": "af9f11964bbeb206a857d1277faac8097c8fb2d3f145b9f7f5424ce08ad783dd" } } ], "extra": [ 1, 83, 219, 105, 99, 103, 224, 244, 42, 32, 202, 34, 146, 252, 31, 65, 233, 205, 163, 18, 128, 77, 51, 48, 130, 142, 33, 49, 129, 137, 245, 201, 165, 2, 17, 0, 0, 0, 34, 173, 67, 58, 11, 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