Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f94265f923cde8b36881ece1815c52cb7829fe1c76d77562dfc80742ed255c25

Tx prefix hash: 3e5b8585276e4ac3561d2230e24dc32c784fa20c1de2877b28cffe1d14a0b372
Tx public key: c138d3a47f7772c52ae9d3ac3b41883ee89a1831658b41d1053c700dfb4a9713
Timestamp: 1582365988 Timestamp [UCT]: 2020-02-22 10:06:28 Age [y:d:h:m:s]: 05:057:22:38:34
Block: 70163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194582 RingCT/type: yes/0
Extra: 01c138d3a47f7772c52ae9d3ac3b41883ee89a1831658b41d1053c700dfb4a9713021100000016d81c26c0000000000000000000

1 output(s) for total of 359.353317364000 dcy

stealth address amount amount idx
00: d81f38955b350410713ea25fdba06569dbb8cb7d9a2cc45f44c50223e462bcf3 359.353317364000 129533 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": 70173, "vin": [ { "gen": { "height": 70163 } } ], "vout": [ { "amount": 359353317364, "target": { "key": "d81f38955b350410713ea25fdba06569dbb8cb7d9a2cc45f44c50223e462bcf3" } } ], "extra": [ 1, 193, 56, 211, 164, 127, 119, 114, 197, 42, 233, 211, 172, 59, 65, 136, 62, 232, 154, 24, 49, 101, 139, 65, 209, 5, 60, 112, 13, 251, 74, 151, 19, 2, 17, 0, 0, 0, 22, 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