Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e98f24ed3684c205c86f883d43f20308b0570b29ee8ef7dc0c2b05f735885e47

Tx prefix hash: 10fc3c97823e8d5290ee4c44f5ebde0adae39eb4bf0a8e37523684d508e2d2b6
Tx public key: b22c0fb38eaea01a2d27dc5d641aaa1c382d1a2eefff0e89c26b23a9ee6fdae9
Timestamp: 1732901560 Timestamp [UCT]: 2024-11-29 17:32:40 Age [y:d:h:m:s]: 00:041:22:32:36
Block: 1164419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29992 RingCT/type: yes/0
Extra: 01b22c0fb38eaea01a2d27dc5d641aaa1c382d1a2eefff0e89c26b23a9ee6fdae9021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b68e3731616fb3330d383ecc7b602bf25afff9d915cfd167eb88bf2da48a4e94 0.600000000000 1650092 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": 1164429, "vin": [ { "gen": { "height": 1164419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b68e3731616fb3330d383ecc7b602bf25afff9d915cfd167eb88bf2da48a4e94" } } ], "extra": [ 1, 178, 44, 15, 179, 142, 174, 160, 26, 45, 39, 220, 93, 100, 26, 170, 28, 56, 45, 26, 46, 239, 255, 14, 137, 194, 107, 35, 169, 238, 111, 218, 233, 2, 17, 0, 0, 0, 4, 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