Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffec6784af5fdfb49feedc29d048d6fac2fc5a0650c250f7420d0a1e3432a726

Tx prefix hash: 506125f13eba01b819aa1a2f5c333062ccb1aacc83c471a86fe344981ccf9c12
Tx public key: 00dc44ac73619960ac376fbcba419f7eb22cefb728f7af21f5a81501ca313d43
Timestamp: 1729375923 Timestamp [UCT]: 2024-10-19 22:12:03 Age [y:d:h:m:s]: 00:219:20:36:48
Block: 1135286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156940 RingCT/type: yes/0
Extra: 0100dc44ac73619960ac376fbcba419f7eb22cefb728f7af21f5a81501ca313d43021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e86f1210a3d74257e8ec464056e44a68b444df993c7242c98a79ef0e2f837f90 0.600000000000 1618621 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": 1135296, "vin": [ { "gen": { "height": 1135286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e86f1210a3d74257e8ec464056e44a68b444df993c7242c98a79ef0e2f837f90" } } ], "extra": [ 1, 0, 220, 68, 172, 115, 97, 153, 96, 172, 55, 111, 188, 186, 65, 159, 126, 178, 44, 239, 183, 40, 247, 175, 33, 245, 168, 21, 1, 202, 49, 61, 67, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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