Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e479d0839b1f665275de8c88150f131ef4b17901974692fa4ab68e0c0dfa25b3

Tx prefix hash: 3701ddf1ba83560a170796b85727f3c202f53b2d3c6c1d5393fc089a186a860c
Tx public key: d12b5c673f3827d4b0ba65bda61962efef8e4fa9b5671a45996a21a9b11222e9
Timestamp: 1631565781 Timestamp [UCT]: 2021-09-13 20:43:01 Age [y:d:h:m:s]: 03:078:01:27:48
Block: 333158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 831399 RingCT/type: yes/0
Extra: 01d12b5c673f3827d4b0ba65bda61962efef8e4fa9b5671a45996a21a9b11222e90211000000014f548792000000000000000000

1 output(s) for total of 48.318082104000 dcy

stealth address amount amount idx
00: 9b44e15507750007c4e5bea5410e5f8f7b280e87e64eddbdc4f3a29046fdd553 48.318082104000 687629 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": 333168, "vin": [ { "gen": { "height": 333158 } } ], "vout": [ { "amount": 48318082104, "target": { "key": "9b44e15507750007c4e5bea5410e5f8f7b280e87e64eddbdc4f3a29046fdd553" } } ], "extra": [ 1, 209, 43, 92, 103, 63, 56, 39, 212, 176, 186, 101, 189, 166, 25, 98, 239, 239, 142, 79, 169, 181, 103, 26, 69, 153, 106, 33, 169, 177, 18, 34, 233, 2, 17, 0, 0, 0, 1, 79, 84, 135, 146, 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