Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffe39c511649f0debc18761b13e2179344cd2cb1a497626a9d29b03603148c7d

Tx prefix hash: 1a42334343c49bdeed8d96b980c44c9f7441f743201aa4ccae45000a037f9070
Tx public key: 47a4f589fe85d897e295585fb0dadbd5e8afb3f8036ffe57750856b0243fbb4c
Timestamp: 1705073435 Timestamp [UCT]: 2024-01-12 15:30:35 Age [y:d:h:m:s]: 01:067:19:12:08
Block: 933795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309576 RingCT/type: yes/0
Extra: 0147a4f589fe85d897e295585fb0dadbd5e8afb3f8036ffe57750856b0243fbb4c02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7472a795a385ca107ac15a1df7a51b2c5392d7b3f519eb5e5bf6c06e810fa7a3 0.600000000000 1391773 of 15

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": 933805, "vin": [ { "gen": { "height": 933795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7472a795a385ca107ac15a1df7a51b2c5392d7b3f519eb5e5bf6c06e810fa7a3" } } ], "extra": [ 1, 71, 164, 245, 137, 254, 133, 216, 151, 226, 149, 88, 95, 176, 218, 219, 213, 232, 175, 179, 248, 3, 111, 254, 87, 117, 8, 86, 176, 36, 63, 187, 76, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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