Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 004f8d0ba59b2fa10696deab4ba5d62b9d7db06e656b4aec21cf327e7399e728

Tx prefix hash: cce5d182b542c7f12520eaec7c4ce59670f775431df5162b45319079be389a36
Tx public key: a2e786a3893dda84e09e52bb2767a99cf5663fea8f5a939d29ffd3670508a527
Timestamp: 1578750606 Timestamp [UCT]: 2020-01-11 13:50:06 Age [y:d:h:m:s]: 04:353:17:43:00
Block: 43269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1142298 RingCT/type: yes/0
Extra: 01a2e786a3893dda84e09e52bb2767a99cf5663fea8f5a939d29ffd3670508a527021100000005d81c26c0000000000000000000

1 output(s) for total of 441.197135433000 dcy

stealth address amount amount idx
00: 53d0424981a0e65b534cc24514a8e70bcd0242ddcdbb1d4dfa64e08f75f3eade 441.197135433000 78282 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": 43279, "vin": [ { "gen": { "height": 43269 } } ], "vout": [ { "amount": 441197135433, "target": { "key": "53d0424981a0e65b534cc24514a8e70bcd0242ddcdbb1d4dfa64e08f75f3eade" } } ], "extra": [ 1, 162, 231, 134, 163, 137, 61, 218, 132, 224, 158, 82, 187, 39, 103, 169, 156, 245, 102, 63, 234, 143, 90, 147, 157, 41, 255, 211, 103, 5, 8, 165, 39, 2, 17, 0, 0, 0, 5, 216, 28, 38, 192, 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