Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f5aa3fb863ebaacc45ef8c78452a2be06f582f28646c30b9716f6eb7c9ca3c9

Tx prefix hash: d111e88119694307dc75338d220d9534e71127986ad6bf2434bfc629903b15c0
Tx public key: 3918f930a7987526a3b79fcb7c479a57fa2a5fa94a8de7f5a0dc3519a310ee73
Timestamp: 1711903299 Timestamp [UCT]: 2024-03-31 16:41:39 Age [y:d:h:m:s]: 01:217:07:53:31
Block: 990444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413981 RingCT/type: yes/0
Extra: 013918f930a7987526a3b79fcb7c479a57fa2a5fa94a8de7f5a0dc3519a310ee730211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b90161882dee4f9f037d5722d1302e9043e87dcd9fd203fb5273bd9ac84c77a9 0.600000000000 1450766 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": 990454, "vin": [ { "gen": { "height": 990444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b90161882dee4f9f037d5722d1302e9043e87dcd9fd203fb5273bd9ac84c77a9" } } ], "extra": [ 1, 57, 24, 249, 48, 167, 152, 117, 38, 163, 183, 159, 203, 124, 71, 154, 87, 250, 42, 95, 169, 74, 141, 231, 245, 160, 220, 53, 25, 163, 16, 238, 115, 2, 17, 0, 0, 0, 1, 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