Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f3663a3044cf61444189e1964a1739ffefcc0bfa255be3aa16844b36dc9ee4f

Tx prefix hash: e52bdc472623130aeab83fce93e0ca68d00f3004b5d028982f8fbae1d16be80c
Tx public key: 22697c0d130429cf1a519d53fb1d12f96765d3625e0ca6d9b62e8d51209c8544
Timestamp: 1707677178 Timestamp [UCT]: 2024-02-11 18:46:18 Age [y:d:h:m:s]: 01:281:19:22:15
Block: 955391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460180 RingCT/type: yes/0
Extra: 0122697c0d130429cf1a519d53fb1d12f96765d3625e0ca6d9b62e8d51209c85440211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 615a2be4c0203afc951a14a49c892e380850ce8bb41343eb0bcd813487c4c5bb 0.600000000000 1414679 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": 955401, "vin": [ { "gen": { "height": 955391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "615a2be4c0203afc951a14a49c892e380850ce8bb41343eb0bcd813487c4c5bb" } } ], "extra": [ 1, 34, 105, 124, 13, 19, 4, 41, 207, 26, 81, 157, 83, 251, 29, 18, 249, 103, 101, 211, 98, 94, 12, 166, 217, 182, 46, 141, 81, 32, 156, 133, 68, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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